home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.dcom.modems
- Path: in2.uu.net!world!geh
- From: geh@world.std.com (Greg E Hersh)
- Subject: Re: Are Comm Overruns Normal?
- Message-ID: <DnLnK4.Lys@world.std.com>
- Organization: The World Public Access UNIX, Brookline, MA
- X-Newsreader: TIN [version 1.2 PL2]
- References: <31375B17.CD5@cris.com>
- Date: Fri, 1 Mar 1996 17:36:03 GMT
-
- Jomo (jbrandt@cris.com) wrote:
- : I was wondering if comm overruns were a fact of life? I thought I had
- : wipped my comm problems by installing wfxcomm.drv (I've got a P90, WFWG
- : 3.11 and a USR Sportster 28800).
-
- : I have reduced the amount of overruns to minimal (20 overruns reported by
- : Trumpet Winsock tracer after 3.5 hours online - heavy use). Does it get
- : any better? I'm tempted to think that there are folks out there who
- : don't ever get overruns. I know I've got a 16550, but I'm only running
- : 57,600 at the serial port and overruns persist, albeit infrequently.
- : Should I bother trying to hunt this one down any further?
-
- : Jomo
-
- I've just finished the testing of USR Sportster 28800, Windows 3.1,
- UART 16C550 from BOCA Research. Had intermittent overruns till I've put
- the following settings into WINDOWS system.ini:
-
- (386Enh section)
-
- com1buffer = 16384
- com1fifo = 1
- comboosttime = 10
-
- Then everything worked just fine, even with a serial port speed
- at 115K. Probably WFWg requires a similar adjustment (I don't have WFWg
- installed on my PC, so I can't tell).
-
- Greg Hersh
-